Method and system for sharing metadata between interfaces

ABSTRACT

A system communicates a client application and a web application and receives configuration data operable within the web application and the client application. The system distributes the configuration data to the client application and the web application. The distributed configuration data is then used to configure the client application and the web application

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/165,359, filed Jan. 27, 2014, which is a continuation of U.S. patentapplication Ser. No. 11/508,420, filed on Aug. 23, 2006, the benefit ofpriority of which is claimed hereby, and of which is incorporated byreference herein in its entirety.

FIELD

This application relates to a method and system for sharing metadatabetween interfaces, and specifically sharing metadata between a clientinterface and a web interface.

BACKGROUND

Network applications are commonly distributed utilizing two differentapproaches, a client application and a web application. For example, aservice or product provider (hereinafter, provider) operating over anetwork (e.g., the Internet) may utilize a client application running ona client device and a web server serving web pages to a client webapplication to exchange various types of data, such as transaction dataor user configuration data.

In the first approach, a client application is created, or hard coded,in a programming language such as C++ and then offered to users as adownload via a network, or distributed by another means such as compactdisk (CD), etc. Once downloaded and/or installed, the user may interactwith the client application in communication with the provider's serverto exchange data. As with most computer applications for users, theclient application is centered on a user interface that providesfunctionality and displays data generated and communicated by theprovider as well as data generated by the user, which may be uploaded tothe provider's server.

In order to provide a consistent user experience for the user of theclient application and the user of a web application, the provider hasto maintain and release new versions of each application whenever achange occurs. Consequently, a provider may incur significant costs intime and resources to ensure a new client application is generated eachtime a change is made to the web application and vice versa.

BRIEF DESCRIPTION OF DRAWINGS

The present embodiments are illustrated by way of example and notlimitation in the figures of the accompanying drawings, in which likereferences indicate similar elements and in which:

FIG. 1 is a network diagram of an example embodiment depicting a dataexchange system having a client-server architecture configured forexchanging data over a network.

FIG. 2A illustrates modules in example embodiment of programmaticframeworks associated with a client application and a web application.

FIG. 2B illustrates an example embodiment of a user interface (UI)screenshot that may be associated with a programmatic framework.

FIG. 2C illustrates an example embodiment of a user interface (UI)screenshot that may be associated with or activated from another UIwithin the programmatic framework.

FIG. 3 illustrates an example embodiment of an options interface and itsrelationship to a UI component.

FIG. 4 illustrates an example embodiment of configuration data that maybe distributed to a web application and a client application to updatetheir respective UI frameworks,

FIG. 5 illustrates an example embodiment of configuration datapropagating from a configuration engine to a framework, and specificallya user interface.

FIG. 6A is a flow chart, according to an example embodiment,illustrating the operations of distributing configuration data to aclient application and a web application

FIG. 6B is a flow chart, according to an example embodiment,illustrating the distribution and use of the configuration data by aclient application and a web application.

FIG. 7 shows a diagrammatic representation of a machine in the exampleform of a computer system within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

DETAILED DESCRIPTION

In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the various embodiments herein. It will be evident,however, to one skilled in the art that these and other embodiments maybe practiced without these specific details.

In one embodiment, a networked system includes a web application anddistributed client applications configured to give their respectiveusers a similar user experience on each application type. To facilitateproviding a similar user experience, a common framework (e.g., userinterface and supporting logic) may be used in each application suchthat a single file containing configuration data (e.g., operationalrules, framework data, UI data, etc.) may be communicated to eachapplication and utilized by each framework to create a substantiallysimilar user experience with respect to the user interface and itsunderlying functionality.

These example embodiments allow for a network system to leverage theadvantages of the client application and the web application. Forexample, a client application has an advantage of being flexible, suchthat a user may interact with the client application offline. On theother hand, a web application dynamically provides user interface datato one or more web clients that can be accessed by any machine on anetwork (e.g., Internet) where the machine includes a web application,such as a common web browser. The dynamic flow of data has a fewadvantages. For example, any change to the user interface may beimplemented on the provider's web server, which seamlessly shows up thenext time the user refreshes or enters the provider's link and downloadsthe new page data. Although this approach provides a lot of flexibilitywith respect to updating functionality, it does not allow for offlineactivities since the application's functionality is derived from datareceived dynamically from the provider's web server,

FIG. 1 is a network diagram depicting a data exchange system 100,according to one embodiment, having a client-server architectureconfigured for exchanging data over a network. For example, the dataexchange system 100 may be a trading/commerce system where clients maycommunicate and exchange data with the trading,/commerce system, thedata may include product listings, auction bids, feedback, etc.

A data exchange platform, in an example form of a network-based provider112, provides server-side functionality, via a network 114 (e.g., theInternet) to one or more clients. The one or more clients may includeusers that may utilize the data exchange system 100, and morespecifically the network-based provider 112, to facilitate dataexchanges, such as various types of transactions (e.g., purchases,listings, feedback. etc.). These data exchanges may be dependent uponuser selected functions available through a client/user interface (UI)(e.g., see FIG. 2B). The UI may be associated with a client machine,such as a client machine 120 utilizing a web client 116 served from aweb application 125 operating on a web server 126. The UI may also beassociated with a client machine 122 utilizing a client application 118,or a third party server 140 hosting a third party application 138.

The web server 126, the client application 118, and the third partyapplication 138 may each host a similar programmatic framework (e.g.,programmatic frameworks 119, 127, 139) to provide a user of the clientmachine 122, third party server 140 or the client machine 120 a similarexperience in functionality for a given transaction. For example, thisfunctionality may include similarities of a particular look and feel ofa user interface (UI) (e.g., what and how data is displayed on the UI,see FIG. 2B), application functionality based on validation rules and/orrolls for the user, programmatic logic to determine a sequence ofactions or displays, and dependency rules to determine what is displayedbased on user interaction. It can be appreciated that in otherembodiments there may be a multitude of web servers 126 operating on oneor more network-based providers 112, but for simplicity a singlenetwork-based providers 112 and a single web server 126 is discussedhereinafter.

In various embodiments, the third party server 140 may or may notinclude the third party application 138. The third party application 138may be remote from the third party server 140 but still be incommunication via the network 114. In one embodiment, the third partyapplication 138 may only include a subset of functionality (e.g., lookand feel of the UI, etc.) that may be associated with the clientapplication 118 and the web application 125. This may provide aprogrammer or administrator of the third party application 138 with theflexibility to pick and choose (if not mandated by the network-basedprovider 112) for its programmatic framework 139 which functions it willhave in common with the programmatic frameworks 119, 127 of the clientapplication 118 and the web application 125, respectively.

Turning specifically to the network-based provider 112, an applicationprogram interface (API) server 124 and a web server 126 are coupled toone or more application servers 128. The application servers 128 hostone or more data exchange and provider applications 129, and one or moreprogrammatic rules application(s) 131. The application servers 128 are,in turn, shown to be coupled to one or more database server(s) 134 thatfacilitate access to one or more database(s) 136.

The programmatic rules application(s) 131 may include a configurationengine 132 that may process configuration data 133 and a distributionmodule 135 to distribute the configuration data 133 to the clientapplication 118, the web application 125 of the web server 126, and thethird party application 138. The configuration data 133 may include butis not limited to framework data, programmatic logic, and validationrules. Once received, the client application 118, the web application125, and the third party application 138 may utilize the configurationdata 133 within their respective programmatic frameworks 119, 127, 139.This may include implementing programmatic changes to existing, oraddition of functionality, to the client applications 118, the thirdparty application 138, and the programmatic components served from theweb application 125 to the web client 116, without having to create anew client application 118, a new third party application 138 and a newweb application 125. In this example embodiment, the client application118, the third party application 138, and the web application 125 may beupdated by a single file or electronic document, such as theconfiguration data 133. Although the configuration data 133 is discussedherein as being distributed via a network, in other embodiments theconfiguration data 133 may be distributed via other distribution media,such as compact disk, floppy disk, flash media, etc. A more detaileddiscussion of embodiments associated with the configuration data 133 isdiscussed below.

The network-based provider 112 may include functionality thatperiodically checks (e.g., via polling) the version of the configurationdata 133 being implemented by the client application 118, the webapplication 125, and the third party application 138. In cases where aparticular application is out of date, the network-based provider 112may push the new configuration data to the out of date application inanother embodiment, the applications may request, automatically or byuser interaction, a configuration data version status. If out of date,the applications may then request the updated version of theconfiguration data 133.

The web client 116 may access the various data exchange and providerapplications 129 and programmatic rules application(s) 131 via the webinterface supported by the web server 126. Similarly, the clientapplication 118 may access the various services and functions providedby the data exchange and provider applications 129 and the programmaticrules application(s) 131 via the programmatic interface provided by theAPI server 124. The client application 118 may, for example, be a sellerapplication (e.g., the TurboLister® application developed by eBay Inc.,of San Jose, Calif.) to enable sellers to author and manage listings atthe network-based provider 112 in an off-line manner, and to performbatch-mode communications between the client application 118 and thenetwork-based provider 112.

As mentioned above, FIG. 1 also illustrates the third party application138, executing on the third party server machine 140, as havingprogrammatic access to the network-based provider 112 via theprogrammatic interface provided by the API server 124. For example, thethird party application 138 may utilize information retrieved from thenetwork-based provider 112 to support one or more features or functionson a website hosted by the third party. The third party website may, forexample, provide one or more promotional, marketplace or paymentfunctions that are supported by the relevant applications of thenetwork-based provider 112.

For simplicity, the discussion hereafter will focus on clientapplication 118 and the web application 125. It can be appreciated thethird party application 138 may have substantially similar functionalityand application to that of the client application 118 with respect tothe various embodiments described herein.

FIG. 2A illustrates modules, according to an example embodiment, of theprogrammatic frameworks 119, 127 associated with the client application122 and the web application 125, respectively. The programmaticframeworks 119, 127 (e.g., a UI framework) may include various types offramework data, which includes but is not limited to modules, such as atitle and category module 204, a pictures and description module 208, aninventory information module 212, and a shipping options module 216.These modules are for example purposes only, and it can be appreciatedthat, in various embodiments, the number and type of modules included ina programmatic framework (e.g., programmatic frameworks 119, 127) may bedependent upon the functions associated with an application of thenetwork-based provider 112. In various embodiments, when these modulesare utilized within their respective frameworks, they may create andprovide various programmatic responses. These programmatic responses mayinclude input/output functions and displays associated with a userinterface, such as a graphical user interface associated with the clientmachines 120, 122.

The title and category module 204, the pictures and description module208, and the inventory information module 212, according to oneembodiment, includes various component sets such as component sets 206,210, 214, respectively. For example, the component set 206 of the titleand category module 204 include a UI component 218 in the form of a textbox, a UI component 220 in the form of a check box, a UI component 222in the form of a ring menu, and a sub-module component 224. Forsimplicity, the component set 210 and the component set 214 includesimilar components as component set 206. However, it can be appreciatedthat in various embodiments, the pictures and description module 208 andthe inventory information module 212 may have less, additional, ordifferent components within their respective component sets (e.g.,component sets 210, 214).

The shipping options module 216 includes specific components that willbe discussed further with reference to FIG. 2B. Specifically, thesecomponents are a rate option UI component 226, a shipping service UIcomponent 228, and a customize sub-module component 230.

In one embodiment, a multitude of category modules and their respectiveUI components are included in the programmatic frameworks 119, 127 upondistribution of their respective applications, the client application118 and the web application 125. The rules (e.g., configuration data133) received and processed by the client application 118 and the webapplication 125 may determine which, if not all, of the multitude ofcategory modules are activated and more specifically which, if not all,of the components of the component sets are used and how they aredisplayed and executed on the client machines (e.g., client machine 120,122). This is how, for example, a single set of rules (e.g.,configuration data 133) may be communicated to two independentapplications (e.g., the client application 118 and the web application125) such that each application maintains substantially similarfunctionality with respect to each other.

Additionally, in other embodiments, new components may be inserted intoone or more existing modules of each framework. For example, theconfiguration data 133 may provide instruction to copy or duplicate anexisting UI component from an existing module and inserted into theexisting or another module. The configuration data 133 may then furtherdefine the new UI component's attributes and functionality as describedherein for updating existing modules and components. In anotherembodiment, a new UI component may be received at the client application118 and web application 125 for addition to the programmatic frameworks119, 127 via the configuration data 133. In yet another embodiment, a UIcomponent may be a generic UI component stored by the client applicationon the host machine and included and defined in the programmaticframework as determined by the configuration data 133.

FIG. 2B illustrates a UT screenshot 231 that may be associated with theprogrammatic frameworks 119, 127, according to an example embodiment.The UI screenshot 231 may include a title and category section 232 thatmay be associated with the title and category module 204 and itscomponent set 206. Similarly, the UI screenshot 231 may include apictures and description interface 234, and an inventory informationinterface 236, which may be associated with the pictures and descriptionmodule 208 and the inventory information module 212.

Although shown here as identical, the UI screenshot 231 may havedifferent look and feel between the two programmatic frameworks 119, 127but still include substantially similar modules and components sets suchthat a single set of rules (e.g., configuration data 133) may be used tomake programmatic changes in each application. For example, the titleand category section 232 in the programmatic framework 119 and theprogrammatic framework 127 may include the UI component 222, which is aring menu, and a Iii component configured as a selectable text box (notshown), each configurable to perform similar functions but using adifferent interface. Although each of the components are common to eachprogrammatic frameworks 119, 127, the set of rules (e.g., theconfiguration data 133) may be used to activate the ring menu UIcomponent for the programmatic framework 119 and the selectable textboxUI component for the programmatic framework 127.

In one embodiment the UI screenshot 231 includes a shipping optionsinterface 238. The shipping options interface 238 may be associated withthe shipping options module 216 of FIG. 2A. The shipping optionsinterface 238 includes a shipping options button 240. In one embodiment,the shipping options button 240 may activate or cause to display ashipping options interface 242 as illustrated in FIG. 2C. The shippingoptions interface 242 corresponds with the shipping options module 216and its associated components. For example, a select a shipping servicering menu 244 corresponds to the shipping service UI component 228 ofthe shipping options module 216. Similarly, a fixed rate ring menu 246may be associated with the rate option UI component 226 of the shippingoptions module 216. Additionally, a customize button 248 may beassociated with the customize sub-module component 230 of the shippingoptions module 216. In one embodiment, the customize sub-modulecomponent 230 when activated by the customize button 248 generates a newinterface which may include additional components, such as UI componentsfor ring menus, check boxes, text boxes etc.

FIG. 3 illustrates an example embodiment of the shipping optionsinterface 242 and its relationship to the shipping service UI component228. The shipping service UI component 22.8 includes underlyingprogrammatic logic and attributes, such as UI component logic andattributes 302. For example, the UI component logic and attributes 302may include operational parameters that when executed within theshipping service UI component 228, cause a shipping options interface242 to display a particular control that may be interacted with by auser. In this example, the control may be the select the shippingservice ring menu 244 and may have attributes such as visibility, color,size, and type (e.g., ring menu). As illustrated in the UI component andlogic attributes 302, the type is a ring menu including three positionseach corresponding to a selectable shipping service (e.g., FedEx®overnight).

Additionally, the UI component logic and attributes 302 may include alogic section 306. The logic section 306 may include programmatic logicor rules for how the programmatic frameworks 119, 127 performs withrespect to what a user may see and do on the client application 122 andthe web client 116. For example, as shown in logic section 306, if thering menu position of the select a shipping service ring menu 244 has aposition value of zero, then a cost field 308 of the shipping optionsinterface 242 may be updated with the United States Postal Service totalrepresenting the cost to ship a particular item.

In various other embodiments, the logic section 306 may include logicsuch that when a particular UI component is activated (e.g., ring menuposition 1 selected) another module or sub-module within theprogrammatic frameworks 119, 127 is activated resulting in an underlyingaction and/or the display of a new user interface or additional userinterface components within an existing interface, such as shippingoptions interface 242. In another example, the customize button ofshipping options interface 242 may be selected by a user. Codified logicwithin the logic section 306 may determine whether or not a newcustomize window opens based on the selection of the customize button248 and the user's (e.g., of client machine 122) access privileges basedon a login and access criteria. It can be appreciated that in variousembodiments many types of attributes and logic may be applied to the UIcomponent logic and attributes 302, and what is illustrated here withrespect to FIG. 3 and its accompanying description is by example only.

FIG. 4 illustrates an example embodiment of the configuration data 133that may be distributed to the web application 125 and the clientapplication 118 to update their respective UI frameworks 127, 119. Auser of computer system 402 may generate the configuration data 133according to a programmatic language utilized by the programmaticframework 127, 119 of the web application 125 and the client application118. For example, the programmatic framework 127, 119 may be implementedin an eXtensible Markup Language (XML) and the configuration data 133may be metadata configured and recognizable by the components (e.g.,shipping service UI component 228) of the modules (e.g., shippingoptions module 216) of the programmatic frameworks 119, 127. It can beappreciated in various embodiments, that the programmatic frameworks119, 127 may be created using one of a multitude of programmaticlanguages such that the configuration data 133 may be utilized to updatethe functionality of the programmatic frameworks 119, 127 of the clientapplication 122 and the web application 125, respectively.

A user of computer system 402, according to one embodiment, may createthe configuration data 133 for distribution to the web application 125and the client application 118. In one embodiment, the configurationdata 133 is stored in the database(s) 136, which then may be accessed bythe programmatic rules application(s) 131 via the database server(s)134. In another embodiment, the computer system 402 is integrated intothe network-based provider 112 and may be in direct communication withthe programmatic rules application(s) 131. The programmatic rulesapplication(s) 131 may provide the programmatic interface to thecomputer system 402 for generating the configuration data 133.

In one embodiment, the configuration engine 132 of the programmaticrules application(s) 131 may format the configuration data 133, asgenerated by computer system 402 and/or retrieve from database(s) 136,into a format usable by the client application 118 and the webapplication 125 and their respective programmatic frameworks 119 and127. The configuration data 133 does not require additional formattingand the configuration engine 132 and the programmatic rulesapplication(s) 131 are utilized to distribute the configuration data 133to the web application 125 and the client application 118. In oneembodiment, the configuration data 133 may be distributed as a text fileover the network 114 to the client application 118 on the client machine122 or within an internal network within the network-based provider 112within communication with the web application 125 within the web server126. In other embodiments, the configuration data 133 is distributed orcommunicated to the web application 125 and the client application 118in one of many types of files known in the art, such as an encryptedfile, a binary file, a text file, etc.

A UI framework update file 401 illustrates an example embodiment of theconfiguration data 133 composed to update a UI component such as the UIcomponent logic and attributes 302 portion of the shipping service UIcomponent 228. In this example, the UI framework update file 401includes an identifier 404. The identifier 404 may be any string oralphanumeric character or other unique identifier indicating which UIcomponent of which module to update in the programmatic frameworks 119,127. The purpose of identifier 404 is to ensure the appropriate UIcomponent in the appropriate module is correctly updated. As illustratedhere, identifier 404 identifies the shipping options module 216 and theshipping service UI component 228.

The UI framework update file 401 may include updates to the variousportions of the UI components, such as updates to the UI component logicand attributes 302 of the shipping service UI component 228. Forexample, an update 408 illustrates an addition to the ring menu ofshipping service UI component 228, and more specifically adds anadditional shipping service that may be selected from the ring menu. Anupdate 410 illustrates a change to the logic section 306 of the UIcomponent logic and attributes 302. Specifically, the update 410 changesthe permissions required for the customization window to be activated.Because the programmatic framework 119 of the client application 118 andthe programmatic framework 127 of the web application 125 aresubstantially similar and share substantially the same modules the sameUI framework update file 401 may be used to update each programmaticframework 119 and 127.

In another embodiment (not shown), and update may include the additionof a new UI component to the programmatic frameworks 119, 127. Forexample, the UI framework update file 401 may include instructions toadd a new UI component from the existing repository associated with theprogrammatic framework, and attribute values to define the UI componentattributes (e.g., UI position of new module, ring menu titles, etc.).The updates and the corresponding file text are only examples of updatesto the attributes and logic section of a UI component within a UI(programmatic) framework, and that many variations in programmatic logicand attributes may exist which may be updated according to the methodsdescribes herein.

FIG. 5 illustrates an example embodiment of the propagation of theconfiguration data 133, and specifically the communication of theexample UI framework update file 401 to the web client 116 and theclient application 122. In this example, the UI framework update file401 is for updating the shipping options interface 242. In variousembodiments, all or a portion of the UI framework update file 401 may beshared between the client application 118 and web application 125. Insuch a manner, particular instructions or data may be targeted to eitheror both of the web client 116 and the client application 122.

The ring menu 502 of the shipping options interface 242 illustrates theaddition of the USPS to the ground option as discussed with reference tothe update 408 in FIG. 4. Additionally, the cost field 504 may also beupdated to reflect the new ring menu selection. Although not shown, theshipping service UI component 228 may include the necessary programmaticfunctions to calculate the cost field 504 and may also have to beupdated accordingly. In other embodiments, the cost field 504 and itscontents are a local or global variable(s) within the programmaticframeworks 119, 127, thus they may be available to other portions of theprogrammatic frameworks 119, 127 (e.g., a calculations module). Theseother portions may be in communication with elements and componentsexternal to the host client machine 120, 122 to acquire data that may benecessary for calculations, inquiries (user or system) etc. (e.g.,obtaining the latest shipping rates from a shipper's web site).

FIG. 6A is a flow chart 600, according to an example embodiment,illustrating the operations of distributing the configuration data 133universal to the client application 118 and the web application 125. Atoperation 602, the server (e.g., application servers 128) receives theconfiguration data operable within the client application 118 and webapplication 125. In one embodiment, the server is communicativelycoupled to the client application 118 and the web application 125 viathe network 114 (e.g., Internet, intranet, etc.). In another embodimentto distribute the configuration data 133, the client machine 122 hostingthe client application 118 (or other networked device, see descriptionwith reference to FIG. 7) may also include applications (e.g., theprogrammatic rules application(s) 131), which may operate in thecapacity of a peer machine in a peer-to-peer (or distributed) networkenvironment, to provide a source for the distribution of theconfiguration data 133.

At operation 604, the server distributes the configuration data 133 tothe client application 118 and the web application 125. Theconfiguration data 133 may then be used to configure the clientapplication 118 and the web application 125. In one embodiment, theserver retrieves the configuration data 133 from a database (e.g.,database(s) 136 via database server(s) 134). In another embodiment, theconfiguration data 133 is generated by a user via a programmaticinterface and distributed to the client application 118 and the webapplication 125 prior to being stored in the database.

FIG. 6B is a flow chart 650, according to an example embodiment,illustrating the distribution and use of the configuration data 133 bythe client application 118 and the web application 125. At operations652 and 654, the client application 118 and the web application 125 arestarted and require updated configuration data. The client application118 and the web application 125 may include a first framework and asecond framework, respectively. Each framework is further composed ofmodules and components which may be executed, in an example embodiment,according to the rules and logic provided by the updatable configurationdata (e.g., configuration data 133).

Based upon a request to the server for updated configuration data or acommand to push the configuration data to the applications, at operation656, the server retrieves the configuration data 133 from a repository,such as database(s) 136. At operation 658, the server sends (e.g., viathe network 114) the configuration data 133 to the client application118 and the web application 125. As discussed above, other embodimentsmay also include communicating the configuration data 133 to the thirdparty application 138.

At operations 660 and 662, the client application 118 and the webapplication 125 receive the configuration data 133. In one embodiment,the configuration data 133 is received over the network 114 as a filerecognizable by each application as a configuration data file. Theclient application 118 and the web application 125 may then use thereceived configuration data 133 to select which of and how the modulesmay be used to generate the desired user interface, including thefunctionality behind the user interface operations. As discussed above,this is done in part through implementing programmatic logic, setting ofUI attributes, etc., via the configuration data 133 and the respectiveframeworks of each application.

FIG. 7 shows a diagrammatic representation of machine in the exampleform of a computer system 700 within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed. In alternative embodiments, themachine operates as a standalone device or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client machine in server-clientnetwork environment, or as a peer machine in a peer-to-peer (ordistributed) network environment. The machine may be a personal computer(PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant(PDA), a cellular telephone, a web appliance, a network router, switchor bridge, or any machine capable of executing a set of instructions(sequential or otherwise) that specify actions to be taken by thatmachine. Further, while only a single machine is illustrated, the termmachine shall also be taken to include any collection of machines thatindividually or jointly execute a set (or multiple sets) of instructionsto perform any one or more of the methodologies discussed herein.

The example computer system 700 includes a processor 702 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 704 and a static memory 706, which communicate witheach other via a bus 708. The computer system 700 may further include avideo display unit 710 (e.g., a liquid crystal display (LCD) or acathode ray tube (CRT)). The computer system 700 also includes analphanumeric input device 712. (e.g., a keyboard), a user interface (UI)navigation device 714 (e.g., a mouse), a disk drive unit 716, a signalgeneration device 718 (e.g., a speaker) and a network interface device720.

The disk drive unit 716 includes a machine-readable medium 722 on whichis stored one or more sets of instructions and data structures (e.g.,software 724) embodying or utilized by any one or more of themethodologies or functions described herein. The software 724 may alsoreside, completely or at least partially, within the main memory 704and/or within the processor 702 during execution thereof by the computersystem 700, the main memory 704 and the processor 702 also constitutingmachine-readable media.

The software 724 may further be transmitted or received over a network726 via the network interface device 720 utilizing any one of a numberof well-known transfer protocols (e.g., HTTP).

While the machine-readable medium 722 is shown in an example embodimentto be a single medium, the term machine-readable medium should be takento include a single medium or multiple media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storethe one or more sets of instructions. The term machine-readable mediumshall also be taken to include any medium that is capable of storing,encoding or carrying a set of instructions for execution by the machineand that cause the machine to perform any one or more of themethodologies of the present invention, or that is capable of storing,encoding or carrying data structures utilized by or associated with sucha set of instructions. The term machine-readable medium shallaccordingly be taken to include, but not be limited to, solid-statememories, optical and magnetic media, and carrier wave signals.

Although an embodiment of the present invention has been described withreference to specific example embodiments, it will be evident thatvarious modifications and changes may be made to these embodimentswithout departing from the broader spirit and scope of the invention.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A computer-implemented method, comprising:receiving configuration data; sending the configuration data to a firstcomputing device associated with a first operating system to cause thefirst computing device to change at least one of a behavior or anappearance of a first application of the first computing device withoutthe first computing device changing a first executable file associatedwith the first application; and sending the configuration data to asecond computing device associated with a second operating system tocause the second computing device to change at least one of acorresponding behavior or a corresponding appearance of a secondapplication of the second computing device without the second computingdevice changing a second executable file associated with the secondclient application.